Launching radio spectrum resources into a fifth generation (5g) network or other next generation networks

ABSTRACT

The technologies described herein are generally directed to launching radio spectrum resources in a fifth generation (5G) network or other next generation networks. For example, a method described herein can include, confirming, by site launching equipment, installation of components of a base station, resulting in a confirmed installation. The method can further comprise, based on the confirmed installation, facilitating, by the site launching equipment, integrating the base station into a communications network. Further, in response to the integrating, launching, by the site launching equipment, operation of the base station for a testing of performance of the base station, the testing resulting in a tested base station. The method can further comprise activating, by the site launching equipment, the tested base station for use by authorized user equipment via the communications network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This non-provisional application claims priority to each of U.S. Provisional Patent Application No. 63/150,175, filed on Feb. 17, 2021, and entitled “LAUNCHING RADIO SPECTRUM RESOURCES INTO A FIFTH GENERATION (5G) NETWORK OR OTHER NEXT GENERATION NETWORKS,” U.S. Provisional Patent Application No. 63/150,178, filed on Feb. 17, 2021, and entitled “CARRIER AGGREGATION CONFIGURATION IN FIFTH GENERATION (5G) NETWORKS OR OTHER NEXT GENERATION NETWORKS,” and U.S. Provisional Patent Application No. 63/150,181, filed on Feb. 17, 2021, and entitled “ALLOCATING RESOURCES TO INTERNET OF THINGS EQUIPMENT IN A FIFTH GENERATION (5G) NETWORK OR OTHER NEXT GENERATION NETWORKS.” The respective entireties of the aforementioned provisional applications are hereby incorporated by reference herein.

TECHNICAL FIELD

The subject application is related to implementation of fifth generation (5G) wireless communication systems or other next generation wireless communication systems, and, for example, different approaches to launching radio spectrum resources into a wireless network.

BRIEF DESCRIPTION OF THE DRAWINGS

The technology described herein is illustrated by way of example and not limited in the accompanying figures in which like reference numerals indicate similar elements and in which:

FIG. 1 is an architecture diagram of an example system that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments.

FIG. 2 is a diagram of a non-limiting example system that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments.

FIG. 3 is a diagram of a non-limiting example process that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments.

FIG. 4 is a diagram of a non-limiting example system that represents a combination of processes described with FIG. 3 above, that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments.

FIG. 5 is a diagram of a non-limiting example system that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments.

FIG. 6 is a diagram of a non-limiting example system that represents a combination of processes described with FIG. 3 above, that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments.

FIG. 7 is a diagram of a non-limiting example system that represents a combination of processes described with FIG. 3 above that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments.

FIG. 8 is a diagram of a non-limiting example system that can facilitate verifying and remediating public land mobile network (PLMN) configuration settings for base station equipment, in accordance with one or more embodiments.

FIG. 9 illustrates an example method that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments.

FIG. 10 depicts an example non-transitory machine-readable medium that can include executable instructions that, when executed by a processor of a system, facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments described above.

FIG. 11 depicts a system where one or more functions of base station equipment described above can be implemented, in accordance with one or more embodiments described above.

FIG. 12 illustrates an example block diagram of an example mobile handset operable to engage in a system architecture that can facilitate processes described herein, in accordance with one or more embodiments.

FIG. 13 illustrates an example block diagram of an example computer operable to engage in a system architecture that can facilitate processes described herein, in accordance with one or more embodiments.

DETAILED DESCRIPTION

Aspects of the subject disclosure will now be described more fully hereinafter with reference to the accompanying drawings in which example components, graphs and selected operations are shown. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments. For example, some embodiments described can facilitate launching radio spectrum resources into a wireless network. Different examples that describe these aspects are included with the description of FIGS. 1-10 below. It should be noted that the subject disclosure may be embodied in many different forms and should not be construed as limited to this example or other examples set forth herein.

Generally speaking, one or more embodiments can facilitate launching radio spectrum resources into a wireless network. In addition, one or more embodiments described herein can be directed towards a multi-connectivity framework that supports the operation of new radio (NR, sometimes referred to as 5G). As will be understood, one or more embodiments can allow an integration of user devices with network assistance, by supporting control and mobility functionality on cellular links (e.g., long term evolution (LTE) or NR). One or more embodiments can provide benefits including but not limited to, system robustness, reduced overhead, and global resource management, while facilitating direct communication links via a NR sidelink.

It should be understood that any of the examples and terms used herein are non-limiting. For instance, while examples are generally directed to non-standalone operation where the NR backhaul links are operating on millimeter wave (mmWave) bands and the control plane links are operating on sub-6 GHz LTE bands, it should be understood that it is straightforward to extend the technology described herein to scenarios in which the sub-6 GHz anchor carrier providing control plane functionality could also be based on NR. As such, any of the examples herein are non-limiting examples, any of the embodiments, aspects, concepts, structures, functionalities or examples described herein are non-limiting, and the technology may be used in various ways that provide benefits and advantages in radio communications in general.

Networks that can be facilitated by one or more implementations described herein can include a wireless communication system, and thus can include one or more communication service provider networks that facilitate providing wireless communication services to various user equipments included in the one or more communication service provider networks. The one or more communication service provider networks can include various types of disparate networks, including but not limited to: cellular networks, femto networks, picocell networks, microcell networks, internet protocol (IP) networks, Wi-Fi service networks, broadband service networks, enterprise networks, cloud-based networks, and the like.

For example, in at least one implementation, system 100 can be used to facilitate the implementation of parts of a large-scale wireless communication network that spans various geographic areas. According to this implementation, the one or more communication service provider networks can be or include the wireless communication network and/or various additional devices and components of the wireless communication network (e.g., additional network devices and cell, additional user equipments, network server devices, etc.). One or more embodiments can facilitate the placement of multiple antennas in a geographic area enabling coverage by networks that include, but are not limited to, communication service provider networks. In exemplary, non-limiting embodiments described herein, simulated groups of antennas can include millimeter wave (mmWave) antennas of a base station of a cellular network, e.g., a fifth generation or other next generation RAN. In certain implementations of types of mmWave antennas, large numbers of antennas are deployed in comparison with the number of other types of antennas that can be employed, e.g., up to and exceeding in some circumstances, one hundred antennas per square mile.

In some embodiments the non-limiting terms “signal propagation equipment” or simply “propagation equipment,” “radio network node” or simply “network node,” “radio network device,” “network device,” and access elements are used herein. These terms may be used interchangeably, and refer to any type of network node that can serve user equipment and/or be connected to other network node or network element or any radio node from where user equipment can receive a signal. Examples of radio network node include, but are not limited to, base stations (BS), multi-standard radio (MSR) nodes such as MSR BS, gNodeB, eNode B, network controllers, radio network controllers (RNC), base station controllers (BSC), relay, donor node controlling relay, base transceiver stations (BTS), access points (AP), transmission points, transmission nodes, remote radio units (RRU) (also termed radio units herein), remote ratio heads (RRH), and nodes in distributed antenna system (DAS). Additional types of nodes are also discussed with embodiments below, e.g., donor node equipment and relay node equipment, an example use of these being in a network with an integrated access backhaul network topology.

In some embodiments, the non-limiting term user equipment (UE) is used. This term can refer to any type of wireless device that can communicate with a radio network node in a cellular or mobile communication system. Examples of UEs include, but are not limited to, a target device, device to device (D2D) user equipment, machine type user equipment, user equipment capable of machine to machine (M2M) communication, PDAs, tablets, mobile terminals, smart phones, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, and other equipment that can have similar connectivity. Example UEs are described further with FIGS. 9 and 10 below. Some embodiments are described in particular for 5G new radio systems. The embodiments are however applicable to any radio access technology (RAT) or multi-RAT system where the UEs operate using multiple carriers, e.g., LTE.

The computer processing systems, computer-implemented methods, apparatus and/or computer program products described herein employ hardware and/or software to solve problems that are highly technical in nature (e.g., performing complex configurations of radio spectrum resources), that are not abstract and cannot be performed as a set of mental acts by a human. For example, a human, or even a plurality of humans, cannot efficiently handle the scale and complexity of configuration at the same level of optimization, accuracy, and/or efficiency as the various embodiments described herein.

Aspects of the subject disclosure will now be described more fully hereinafter with reference to the accompanying drawings in which example components, graphs and selected operations are shown. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments. For example, some embodiments described can facilitate launching radio spectrum resources into a wireless network. It should be noted that the subject disclosure may be embodied in many different forms and should not be construed as limited to this example or other examples set forth herein.

The above-described background relating to network hardware is merely intended to provide a contextual overview of some current issues, and is not intended to be exhaustive. Other contextual information may become further apparent upon review of the following detailed description.

Transitioning a radio spectrum resource of a communications network from construction and equipment installation to use in production can require performance of different combinations of hundreds of procedures, tests, and requirement checks. Generally speaking, one of the benefits of one or more embodiments is automatically performing analysis, selection, scheduling, and performance of different combinations of these elements, in certain circumstances. It should be noted that, although many examples herein discuss requirements, testing and implementation of base station equipment resources, one having skill in the relevant art(s), given the description herein would appreciate that the approaches can also apply to other elements of current and future communication networks, e.g., arrays of femto cells and other elements of fifth generation and later generation networks.

FIG. 1 is an architecture diagram of an example system 100 that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments. For purposes of brevity, description of like elements and/or processes employed in other embodiments is omitted.

As depicted, system 100 can include site launching equipment 150 communicatively coupled to base station equipment 180 via network 190. In one or more embodiments, site launching equipment 150 can include computer-executable components 120, processor 160, storage device 170, and memory 165.

Computer-executable components 120 can include triggering event component 122, installation confirmation component 124, network integration component 126, soft launch component 127, activation component 128, and other components described or suggested by different embodiments described herein that can facilitate or improve the operation of system 100. It should be appreciated that these components, as well as aspects of the embodiments of the subject disclosure depicted in this figure and various figures disclosed herein, are for illustration only, and as such, the architecture of such embodiments are not limited to the systems, devices, and/or components depicted therein. For example, in some embodiments, site launching equipment 150 can further comprise various computer and/or computing-based elements described herein with reference to operating environment 1300 and FIG. 13.

According to multiple embodiments, network 190 can comprise, but is not limited to, wired (including optical) and wireless networks, including, but not limited to, a cellular network, a wide area network (WAN) (e.g., the Internet) or a local area network (LAN). For example, system 100 can communicate with one or more external systems, sources, and/or devices, for instance, computing devices (and vice versa) using virtually any desired wired or wireless technology, including but not limited to: wireless fidelity (Wi-Fi), global system for mobile communications (GSM), universal mobile telecommunications system (UMTS), worldwide interoperability for microwave access (WiMAX), enhanced general packet radio service (enhanced GPRS), third generation partnership project (3GPP) long term evolution (LTE) or 5G, third generation partnership project 2 (3GPP2) ultra-mobile broadband (UMB), high speed packet access (HSPA), Zigbee and other 802.XX wireless technologies and/or legacy telecommunication technologies, BLUETOOTH®, Session Initiation Protocol (SIP), ZIGBEE®, RF4CE protocol, WirelessHART protocol, 6LoWPAN (IPv6 over Low power Wireless Area Networks), Z-Wave, an ANT, an ultra-wideband (UWB) standard protocol, and/or other proprietary and non-proprietary communication protocols.

In some embodiments, memory 165 can comprise volatile memory (e.g., random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), etc.) and/or non-volatile memory (e.g., read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), etc.) that can employ one or more memory architectures. Further examples of memory 165 are described below with reference to system memory 1306 and FIG. 13. Such examples of memory 165 can be employed to implement any embodiments of the subject disclosure.

According to multiple embodiments, storage device 170 can include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, solid state drive (SSD) or other solid-state storage technology, Compact Disk Read Only Memory (CD ROM), digital video disk (DVD), blu-ray disk, or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer.

According to multiple embodiments, processor 160 can comprise one or more processors and/or electronic circuitry that can implement one or more computer and/or machine readable, writable, and/or executable components and/or instructions that can be stored on memory 165. For example, processor 160 can perform various operations that can be specified by such computer and/or machine readable, writable, and/or executable components and/or instructions including, but not limited to, logic, control, input/output (I/O), arithmetic, and/or the like. In some embodiments, processor 160 can comprise one or more components including, but not limited to, a central processing unit, a multi-core processor, a microprocessor, dual microprocessors, a microcontroller, a system on a chip (SOC), an array processor, a vector processor, and other types of processors. Further examples of processor 160 are described below with reference to processing unit 1304 of FIG. 13. Such examples of processor 160 can be employed to implement any embodiments of the subject disclosure.

According to multiple embodiments, site launching equipment 150 can include memory 165 that can store one or more computer and/or machine readable, writable, and/or executable components and/or instructions 120 that, when respectively executed by processor 160, can facilitate performance of operations defined by the executable component(s) and/or instruction(s).

Generally, applications (e.g., computer-executable components 120) can include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the methods described herein can be practiced with other system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

It should be appreciated that the embodiments of the subject disclosure depicted in various figures disclosed herein are for illustration only, and as such, the architecture of such embodiments are not limited to the systems, devices, and/or components depicted therein. For example, in some embodiments, site launching equipment 150 can further comprise various computer and/or computing-based elements described herein with reference to operating environment 1300 and FIG. 13. In one or more embodiments, such computer and/or computing-based elements can be used in connection with implementing one or more of the systems, devices, components, and/or computer-implemented operations shown and described in connection with FIG. 1 or other figures disclosed herein.

For example, in one or more embodiments, computer-executable components 120 can be used in connection with implementing one or more of the systems, devices, components, and/or computer-implemented operations shown and described in connection with FIG. 1 or other figures disclosed herein. For example, in one or more embodiments, computer-executable components 120 can include instructions that, when executed by processor 160, can facilitate performance of operations defining triggering event component 122. As discussed with FIGS. 2 and 3 below, triggering event component 122 can, in accordance with one or more embodiments, obtain notice data representative of a notice of completion of a regulatory milestone for the installation of the components of the base station, with confirming the installation process being triggered in response to obtaining the notice data.

In another example, in one or more embodiments, computer-executable components 120 can include instructions that, when executed by processor 160, can facilitate performance of operations defining installation confirmation component 124. As discussed below (e.g., with FIGS. 5), installation confirmation component 124 can, in accordance with one or more embodiments, confirm, by site launching equipment comprising a processor, installation of components of a base station, resulting in a confirmed installation.

In another example, in one or more embodiments, computer-executable components 120 can include instructions that, when executed by processor 160, can facilitate performance of operations defining network integration component 126. As discussed below (e.g., with FIG. 6), network integration component 126 can, in accordance with one or more embodiments, based on the confirmed installation, facilitate, by the site launching equipment, integrating the base station into a communications network.

In another example, in one or more embodiments, computer-executable components 120 can include instructions that, when executed by processor 160, can facilitate performance of operations defining soft launch component 127. As discussed below (e.g., with FIGS. 6-7), soft launch component 127 can, in accordance with one or more embodiments, in response to the integrating, launch, by the site launching equipment, operation of the base station for a testing of performance of the base station, the testing resulting in a tested base station.

In another example, in one or more embodiments, computer-executable components 120 can include instructions that, when executed by processor 160, can facilitate performance of operations defining activation component 128. As discussed below (e.g., with FIG. 7), activation component 128 can, in accordance with one or more embodiments, activate, by the site launching equipment, the tested base station for use by authorized user equipment via the communications network.

It should be noted that, in one or more embodiments, system 100 and other embodiments described herein can employ hardware and/or software to solve problems that are highly technical in nature, including improving the launching of base station equipment 180. One having skill in the relevant art(s), given the disclosure herein, would appreciate that the technical problems that can be solved by one or more embodiments described herein are not abstract and cannot be performed as a set of mental acts by a human.

Further, in certain embodiments, some of the processes performed can be performed by one or more specialized computers (e.g., one or more specialized processing units, a specialized computer such as tomography and reconstruction, statistical estimation, specialized routing analysis, and so on) for carrying out defined tasks related to launching radio spectrum resources into a wireless network. System 100 and/or components of the system can be employed to solve new problems that arise through advancements in technologies mentioned above, computer architecture, and/or the like.

The above-described background relating to network hardware is merely intended to provide a contextual overview of some current issues, and is not intended to be exhaustive. Other contextual information may become further apparent upon review of the following detailed description.

FIG. 2 is a diagram of a non-limiting example system 200 that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments. For purposes of brevity, description of like elements and/or processes employed in other embodiments is omitted.

According to multiple embodiments, base station equipment 180 can include memory 165 that can store one or more computer and/or machine readable, writable, and/or executable components and/or instructions 220 that, when respectively executed by processor 160, can facilitate performance of operations defined by the executable component(s) and/or instruction(s). Base station equipment 180 can further include transceiver 285.

Computer-executable components 220 can include self-correcting network process manager 222, soft launch testing component 224, milestone completion component 226, activation component 228, and other components described or suggested by different embodiments described herein that can improve the operation of system 100. It should be appreciated that these components, as well as aspects of the embodiments of the subject disclosure depicted in this figure and various figures disclosed herein, are for illustration only, and as such, the architecture of such embodiments are not limited to the systems, devices, and/or components depicted therein. For example, in some embodiments, site launching equipment 150 can further comprise various computer and/or computing-based elements, for example as described herein with reference to operating environment 1300 and FIG. 13. It may also encompass various computer and/or computing-based elements associated with the site launching equipment 150 in FIG. 1, in other embodiments.

For example, in one or more embodiments, computer-executable components 220 can be used in connection with implementing one or more of the systems, devices, components, and/or computer-implemented operations shown and described in connection with FIG. 2 or other figures disclosed herein. For example, in one or more embodiments, computer-executable components 220 can include instructions that, when executed by processor 160, can facilitate performance of operations defining self-correcting network process manager 222. As discussed with FIGS. 2 and 3 below, self-correcting network process manager 222 can, in accordance with one or more embodiments, instruct the base station to perform a self-correcting network process at the base station to reduce the likelihood to being less than the threshold likelihood.

In another example, in one or more embodiments, computer-executable components 220 can include instructions that, when executed by processor 160, can facilitate performance of operations defining soft launch testing component 224. As discussed below, soft launch testing component 224 can, in accordance with one or more embodiments, receive (e.g., by transceiver 285), from the network implementation equipment, second instruction data representing a second instruction to launch an operation of a transceiver used by the network equipment to test a performance of communicating with the network implementation equipment using the transceiver.

In another example, in one or more embodiments, computer-executable components 220 can include instructions that, when executed by processor 160, can facilitate performance of operations defining milestone completion component 226. As discussed below, milestone completion component 226 can, in accordance with one or more embodiments, transmit information usable to confirm the installation of the site components, based on a determination that a regulatory milestone for the installation of the components of the network equipment has been reached.

FIG. 3 is a diagram of a non-limiting example process 300 that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments. For purposes of brevity, description of like elements and/or processes employed in other embodiments is omitted.

In the example depicted, process 300 includes triggering event 301, install confirmation 302, network integration 308, soft launch 310, launch testing 312, and activation 314, e.g., general elements that one or more embodiments can perform to facilitate launching radio spectrum resources into a wireless network. It should be noted that the above elements are examples of one way that different actions performed by one or more embodiments can be performed, and additional or fewer actions than are discussed herein can be performed without departing from the spirit of embodiments described herein.

Triggering event 301 can describe one or more embodiments obtaining (e.g., by triggering event component 122 of site launching equipment 150) notice data representative of a notice of completion of a milestone, such as a regulatory, financial, or construction milestone, for the installation of the components of the base station. As described below with FIG. 4, in one or more embodiments, the process of confirming the installation process (e.g., install confirmation 302) can be triggered in response to this obtaining of the notice data.

Install confirmation 302 can describe one or more embodiments confirming (e.g., by installation confirmation component 124 of site launching equipment 150) installation of components of a base station, resulting in a confirmed installation. For example, as described with FIG. 5 below, one or more embodiments can collect and analyze information associated with confirming the installation of components of base station equipment 180.

Network integration 308 can describe one or more embodiments (e.g., by network integration component 126 of site launching equipment 150), based on the confirmed installation, facilitating, by the site launching equipment, integrating the base station into a communications network. For example, as described with FIG. 6 below, one or more embodiments can, based on a confirmed installation of components of base station equipment 180 and specified tests, base station equipment 180 can be integrated into the communications network depicted in systems 100 and 200.

Soft launch 310 can describe one or more embodiments launching (e.g., by soft launch component 127 of site launching equipment 150), in response to the integrating, operation of the base station for a testing of performance of the base station, the testing resulting in a tested base station. For example, as described with FIG. 6 below, one or more embodiments can, perform a launch of base station equipment 180 so as to provide launch testing 312. Launch testing 312 can describe one or more embodiments utilizing soft launch component 127 to cause soft launch component 224 (e.g., of base station equipment 180) to test a performance of communicating with elements of the telecommunications network using transceiver 285 of base station equipment 180. As described further with FIG. 6 below, soft launch testing can perform specified tests to facilitate activation of base station equipment 180, e.g., by activation 314. Activation 314 can describe one or more embodiments activating (e.g., by activation component 128 of site launching equipment 150) the tested base station for use by authorized user equipment via the communications network. For example, with FIG. 7 below, different example tests and other activities that can be performed for activation of base station equipment 180 are described.

FIG. 4 is a diagram of a non-limiting example system 400 that represents a combination of processes described with FIG. 3 above, that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments. For purposes of brevity, description of like elements and/or processes employed in other embodiments is omitted. As depicted, system 400 includes triggering event 301 and install confirmation 302. As discussed further below, triggering event 301 includes reference to milestone-based triggers 410, automated standard pre-checks 430, and auto-remediations.

As discussed above, one or more embodiments can analyze and manage combinations of processes and tests that are typically performed for spectrum resource of a communications network from construction and equipment installation to use in production. Further to these functions, one or more embodiments can automatically initiate the management and performance of post-installation processes based on one or more triggering events detectable by system 400.

Rather than rely on narrative reports of the occurrence of different events, different embodiments can utilize centralized sources of information regarding certain types of activities, e.g., compliance with certain government regulations and audits performed in accordance with enterprise management of projects. For example, one regulatory requirement that must be performed for some implementations of base station equipment 180 is the performance of enhanced 911 (E911) compliance steps, e.g., provisioning, auditing, and testing (e.g., drive testing).

For example, in one or more embodiments, as a function of the completion of the installation of components E911 testing and compliance records are stored a database accessible to site launching equipment 150. In some implementations, upon detection of triggering records (e.g., compliance actualized 420C) by site launching equipment 150, system 100 can determine the components have been installed to the point that installation confirmation processes are required, e.g., transitioning to the processes described below with install confirmation 302.

One advantage that can result from the ‘pull’ approach (e.g., embodiments querying data sources at different intervals) is that embodiments do not rely upon affirmative reports of the completion of steps (e.g., these can be unreliable or be delayed). In contrast, some regulatory requirements, having penalties associated with unreliable or delays reporting, can be a more responsive trigger for efficient action by embodiments.

Alternatively, other triggering events can be utilized, including enterprise-specific records, e.g., stored in project management record systems, e.g., integration actualized 420A and audits actualized 420B. In a variation of this approach, triggering events can be pushed to site launching equipment 150, e.g., by enterprise project management systems. Different benefits can result from embodiments receiving reports of triggering events, e.g., a reduction in overhead based on not having to perform regular queries.

FIG. 5 is a diagram of a non-limiting example system 500 that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments. For purposes of brevity, description of like elements and/or processes employed in other embodiments is omitted. As depicted system 500 includes install confirmation 302 discussed above, along with three different examples of installation checks performed, e.g., hardware (HW) installation check 512, design vs. implementation audit 517, and alarms and parameter checks 522.

As depicted, the example checks included include checks that can be mandated by government regulations as well as checks that can be used by project management systems to confirm completion of differed installation stages. It should be appreciated that, in some embodiments described herein, the requirements managed and performed at a particular phase (e.g., install confirmation 302, network integration 308, soft launch 310, and activation 314) are selected so as to reduce the risk of transitioning to the next phase in the process. For example, as discussed further below the phase following install confirmation 302 is network integration 308.

Thus, in an example install confirmation 302, different requirements can be selected by one or more embodiments that can reduce the likelihood of an adverse event occurring at network integration 308, e.g., faults that could either damage the installed hardware, interfere with other assets (e.g., correct site name per naming specification 515D, or otherwise prevent network integration from occurring successfully, e.g., fiber quality (UL/DL loss) 510B, RSSI correction on all receiving ports on all sectors 510E.

In an alternative approach that can be combined with the above selection criteria, in one or more embodiments, checks can be performed that are specific confirmation that installation and configuration of base station equipment 180 components was performed as required, e.g., antenna GPS OK 515E, base station software (SW) license key file is current 515G. In another approach that can be combined with the above noted approaches, checks can be selected for install confirmation 302 that reflect regulatory requirements for the particular phase, e.g., PLMN primary and additional defined correctly.

It should be appreciated that these example approaches to selecting and managing requirements for install confirmation 302 can be used for any of the phases (e.g., collections of requirements) described herein, e.g., reduce likelihood of adverse events in a later stage, general checking on completion of stage, and regulatory requirements of a particular stage.

FIG. 6 is a diagram of a non-limiting example system 600 that represents a combination of processes described with FIG. 3 above, that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments. For purposes of brevity, description of like elements and/or processes employed in other embodiments is omitted.

As depicted, system 600 includes network integration 308 and soft launch 310, with the former including example activities, configuration management 620A, auto remediation 620B, self-correcting software 620C, new sites automatically prioritized 620D, pre-launch fault management 620E, and exception process for failures 620F, and the latter including automatic creation of testing geo-fence 630A, automated launch for testing 630B, and initiate post launch KPI/alarms collection 630C. System 600 also includes launch testing 312.

FIG. 7 is a diagram of a non-limiting example system 700 that represents a combination of processes described with FIG. 3 above that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments. For purposes of brevity, description of like elements and/or processes employed in other embodiments is omitted.

As depicted, system 700 includes launch testing 312 and activation 314, with the former including automated KPI and alarm analytics 710A, periodic automated email reporting 710B, intelligent lock down based on submarket profile 710C, and the latter including automated optimization 740 and key launch variables 745. System 600 also includes launch testing 312.

FIG. 8 is a diagram of a non-limiting example system 800 that can facilitate verifying and remediating public land mobile network (PLMN) configuration settings for base station equipment, in accordance with one or more embodiments. For purposes of brevity, description of like elements and/or processes employed in other embodiments is omitted. System 800 can include site launching equipment 150 communicatively coupled to base station equipment 180, with site launching equipment 150 having the computer-executable components described with FIG. 1 above, with the addition of PLMN state management component 810.

As would be appreciated by one having skill in the relevant art(s), given the present disclosure, to successfully provide different services to subscribers, base station equipment must have correctly set PLMN configuration settings. Incorrect settings can cause problems ranging from limiting connectivity to the base station by permitted devices to a degradation in the capabilities of government regulated emergency communications provided by the base station. Other problems that can be caused by PLMN configuration issues include, but are not limited to, commercial subscribers granted access to cells not yet ready for commercial use, and commercial subscribers only provided partial access to cells intended for full commercial use, e.g., subscribers having all feature functionality of the core network available to them.

Example circumstances where PLMN settings can be configured in error is in the transition from launch testing 312 to activation 314 discussed above with the discussion of site launching equipment 150. Errors can occur because one way to facilitate launch testing (e.g., the provision of services by a base station to a smaller group of devices) is to use a PLMN configuration that only permits certain devices to establish connections to the base station.

In one or more embodiments, because incorrect settings can result from the processes involve in launching wireless resources, one or more embodiments can include PLMN state management component 810 as a component of computer-executable components 120 discussed throughout this application. Different processes that can be performed by PLMN state management component include, but are not limited to, retrieving PLMN settings of base station equipment 180 and identifying erroneous PLMN configurations, and remediating erroneous PLMN configurations.

FIG. 9 illustrates an example method 900 that can facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments. For purposes of brevity, description of like elements and/or processes employed in other embodiments is omitted.

At 902, method 900 can include, confirming, by site launching equipment comprising a processor, installation of components of a base station, resulting in a confirmed installation. At 904, method 900 can include, based on the confirmed installation, facilitating, by the site launching equipment, integrating the base station into a communications network. At 906, method 900 can include, in response to the integrating, launching, by the site launching equipment, operation of the base station for a testing of performance of the base station, the testing resulting in a tested base station. At 908, method 900 can include, activating, by the site launching equipment, the tested base station for use by authorized user equipment via the communications network.

FIG. 10 depicts an example 1000 non-transitory machine-readable medium 1010 that can include executable instructions that, when executed by a processor of a system, facilitate launching radio spectrum resources into a wireless network, in accordance with one or more embodiments described above. For purposes of brevity, description of like elements and/or processes employed in other embodiments is omitted. As depicted, non-transitory machine-readable medium 1010 includes executable instructions that can facilitate performance of operations 1002-1006.

In one or more embodiments, the operations can include operation 1002 that can, based on an indication that base station equipment complies with a regulatory requirement for use in a mobile network, confirm that components of the base station equipment have been installed, wherein the confirming comprises comparing a specified installation parameter to a measured parameter determined for the base station equipment, and wherein the confirming results in a confirmed installation of the base station equipment. The operations can further include operation 1004 that can, based on the confirmed installation, facilitating commencing operation of the base station equipment to test a performance of the base station equipment, wherein a result of testing the performance is used to estimate a likelihood of an activation of the base station equipment for usage by user devices in the mobile network causing a defined adverse event. The operations can further include operation 1004 that can, based on the likelihood being less than a defined threshold, facilitating activating the base station equipment for the usage in mobile network.

FIG. 11 depicts a system 1100 where one or more functions of base station equipment 180 described above can be implemented by computer-executable components 120, in accordance with one or more embodiments described above. For purposes of brevity, description of like elements and/or processes employed in other embodiments is omitted.

In one or more embodiments, site launching components of base station equipment 180 can be implemented in a software platform that includes several interconnected components. As depicted, system 1100 can include milestone completion component 226, self-correcting network process manager 222, soft launch component 224, and activation component 228.

In an example, operations 1102 and 1104 can include the functions of milestone completion component 226 of base station equipment 180, supported by the other layers of system 1100 and embodiments described herein. For example, operation 1102 can facilitate transmitting, to network implementation equipment, information usable to confirm installation of components of the network equipment. Continuing this example, 1104 can, in response to the transmitting, receive, from the network implementation equipment, confirmation data representing that the installation of the component has been confirmed by the network implementation equipment.

In another example, operation 1106 can include the functions of self-correcting network process manager 222 of base station equipment 180, supported by the other layers of system 1100 and embodiments described herein. For example, operation 1106 can facilitate receiving, from the network implementation equipment, first instruction data representing a first instruction to integrate the network equipment into a telecommunications network.

In yet another example, operations 1108 can include the functions of soft launch component 224 of base station equipment 180, supported by the other layers of system 1100 and embodiments described herein. For example, operation 1108 can facilitate, based on the monitored slice performance, a recalibrating of the resource profile in accordance with a condition associated with the network service type, resulting in a modification of the capacity of the resource assigned to the network slice

In yet another example, operations 1110 can include the functions of activation component 228 of base station equipment 180, supported by the other layers of system 1100 and embodiments described herein. For example, operation 1108 can facilitate, based on the monitored slice performance, a recalibrating of the resource profile in accordance with a condition associated with the network service type, resulting in a modification of the capacity of the resource assigned to the network slice.

FIG. 12 illustrates an example block diagram of an example mobile handset 1200 operable to engage in a system architecture that facilitates wireless communications according to one or more embodiments described herein. Although a mobile handset is illustrated herein, it will be understood that other devices can be a mobile device, and that the mobile handset is merely illustrated to provide context for the embodiments of the various embodiments described herein. The following discussion is intended to provide a brief, general description of an example of a suitable environment in which the various embodiments can be implemented. While the description includes a general context of computer-executable instructions embodied on a machine-readable storage medium, those skilled in the art will recognize that the embodiments also can be implemented in combination with other program modules and/or as a combination of hardware and software.

Generally, applications (e.g., program modules) can include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the methods described herein can be practiced with other system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices

A computing device can typically include a variety of machine-readable media. Machine-readable media can be any available media that can be accessed by the computer and includes both volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, computer-readable media can comprise computer storage media and communication media. Computer storage media can include volatile and/or non-volatile media, removable and/or non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data. Computer storage media can include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, solid state drive (SSD) or other solid-state storage technology, Compact Disk Read Only Memory (CD ROM), digital video disk (DVD), Blu-ray disk, or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer. In this regard, the terms “tangible” or “non-transitory” herein as applied to storage, memory or computer-readable media, are to be understood to exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.

Communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media

The handset includes a processor 1202 for controlling and processing all onboard operations and functions. A memory 1204 interfaces to the processor 1202 for storage of data and one or more applications 1206 (e.g., a video player software, user feedback component software, etc.). Other applications can include voice recognition of predetermined voice commands that facilitate initiation of the user feedback signals. The applications 1206 can be stored in the memory 1204 and/or in a firmware 1208, and executed by the processor 1202 from either or both the memory 1204 or/and the firmware 1208. The firmware 1208 can also store startup code for execution in initializing the handset 1200. A communications component 1210 interfaces to the processor 1202 to facilitate wired/wireless communication with external systems, e.g., cellular networks, VoIP networks, and so on. Here, the communications component 1210 can also include a suitable cellular transceiver 1211 (e.g., a GSM transceiver) and/or an unlicensed transceiver 1213 (e.g., Wi-Fi, WiMax) for corresponding signal communications. The handset 1200 can be a device such as a cellular telephone, a PDA with mobile communications capabilities, and messaging-centric devices. The communications component 1210 also facilitates communications reception from terrestrial radio networks (e.g., broadcast), digital satellite radio networks, and Internet-based radio services networks

The handset 1200 includes a display 1212 for displaying text, images, video, telephony functions (e.g., a Caller ID function), setup functions, and for user input. For example, the display 1212 can also be referred to as a “screen” that can accommodate the presentation of multimedia content (e.g., music metadata, messages, wallpaper, graphics, etc.). The display 1212 can also display videos and can facilitate the generation, editing and sharing of video quotes. A serial I/O interface 1214 is provided in communication with the processor 1202 to facilitate wired and/or wireless serial communications (e.g., USB, and/or IEEE 1294) through a hardwire connection, and other serial input devices (e.g., a keyboard, keypad, and mouse). This supports updating and troubleshooting the handset 1200, for example. Audio capabilities are provided with an audio I/O component 1216, which can include a speaker for the output of audio signals related to, for example, indication that the user pressed the proper key or key combination to initiate the user feedback signal. The audio I/O component 1216 also facilitates the input of audio signals through a microphone to record data and/or telephony voice data, and for inputting voice signals for telephone conversations.

The handset 1200 can include a slot interface 1218 for accommodating a SIC (Subscriber Identity Component) in the form factor of a card Subscriber Identity Module (SIM) or universal SIM 1220, and interfacing the SIM card 1220 with the processor 1202. However, it is to be appreciated that the SIM card 1220 can be manufactured into the handset 1200, and updated by downloading data and software.

The handset 1200 can process IP data traffic through the communications component 1210 to accommodate IP traffic from an IP network such as, for example, the Internet, a corporate intranet, a home network, a person area network, etc., through an ISP or broadband cable provider. Thus, VoIP traffic can be utilized by the handset 1200 and IP-based multimedia content can be received in either an encoded or a decoded format.

A video processing component 1222 (e.g., a camera) can be provided for decoding encoded multimedia content. The video processing component 1222 can aid in facilitating the generation, editing, and sharing of video quotes. The handset 1200 also includes a power source 1224 in the form of batteries and/or an AC power subsystem, which power source 1224 can interface to an external power system or charging equipment (not shown) by a power I/O component 1226.

The handset 1200 can also include a video component 1230 for processing video content received and, for recording and transmitting video content. For example, the video component 1230 can facilitate the generation, editing and sharing of video quotes. A location tracking component 1232 facilitates geographically locating the handset 1200. As described hereinabove, this can occur when the user initiates the feedback signal automatically or manually. A user input component 1234 facilitates the user initiating the quality feedback signal. The user input component 1234 can also facilitate the generation, editing and sharing of video quotes. The user input component 1234 can include such conventional input device technologies such as a keypad, keyboard, mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 1206, a hysteresis component 1236 facilitates the analysis and processing of hysteresis data, which is utilized to determine when to associate with the access point. A software trigger component 1238 can be provided that facilitates triggering of the hysteresis component 1236 when the Wi-Fi transceiver 1213 detects the beacon of the access point. A SIP client 1240 enables the handset 1200 to support SIP protocols and register the subscriber with the SIP registrar server. The applications 1206 can also include a client 1242 that provides at least the capability of discovery, play and store of multimedia content, for example, music.

The handset 1200, as indicated above related to the communications component 1210, includes an indoor network radio transceiver 1213 (e.g., Wi-Fi transceiver). This function supports the indoor radio link, such as IEEE 802.11, for the dual-mode GSM handset 1200. The handset 1200 can accommodate at least satellite radio services through a handset that can combine wireless voice and digital radio chipsets into a single handheld device.

Network 190 can employ various cellular systems, technologies, and modulation schemes to facilitate wireless radio communications between devices. While example embodiments include use of 5G new radio (NR) systems, one or more embodiments discussed herein can be applicable to any radio access technology (RAT) or multi-RAT system, including where user equipments operate using multiple carriers, e.g., LTE FDD/TDD, GSM/GERAN, CDMA2000, etc. For example, wireless communication system 200 can operate in accordance with global system for mobile communications (GSM), universal mobile telecommunications service (UMTS), long term evolution (LTE), LTE frequency division duplexing (LTE FDD, LTE time division duplexing (TDD), high speed packet access (HSPA), code division multiple access (CDMA), wideband CDMA (WCMDA), CDMA2000, time division multiple access (TDMA), frequency division multiple access (FDMA), multi-carrier code division multiple access (MC-CDMA), single-carrier code division multiple access (SC-CDMA), single-carrier FDMA (SC-FDMA), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-spread OFDM) single carrier FDMA (SC-FDMA), Filter bank based multi-carrier (FBMC), zero tail DFT-spread-OFDM (ZT DFT-s-OFDM), generalized frequency division multiplexing (GFDM), fixed mobile convergence (FMC), universal fixed mobile convergence (UFMC), unique word OFDM (UW-OFDM), unique word DFT-spread OFDM (UW DFT-Spread-OFDM), cyclic prefix OFDM CP-OFDM, resource-block-filtered OFDM, Wi Fi, WLAN, WiMax, and the like. However, various features and functionalities of system 100 are particularly described wherein the devices of system 100 are configured to communicate wireless signals using one or more multi carrier modulation schemes, wherein data symbols can be transmitted simultaneously over multiple frequency subcarriers (e.g., OFDM, CP-OFDM, DFT-spread OFMD, UFMC, FMBC, etc.). The embodiments are applicable to single carrier as well as to multicarrier (MC) or carrier aggregation (CA) operation of the user equipment. The term carrier aggregation (CA) is also called (e.g., interchangeably called) “multi-carrier system”, “multi-cell operation”, “multi-carrier operation”, “multi-carrier” transmission and/or reception. Note that some embodiments are also applicable for Multi RAB (radio bearers) on some carriers (that is data plus speech is simultaneously scheduled).

Various embodiments described herein can be configured to provide and employ 5G wireless networking features and functionalities. With 5G networks that may use waveforms that split the bandwidth into several sub bands, different types of services can be accommodated in different sub bands with the most suitable waveform and numerology, leading to improved spectrum utilization for 5G networks. Notwithstanding, in the mmWave spectrum, the millimeter waves have shorter wavelengths relative to other communications waves, whereby mmWave signals can experience severe path loss, penetration loss, and fading. However, the shorter wavelength at mmWave frequencies also allows more antennas to be packed in the same physical dimension, which allows for large-scale spatial multiplexing and highly directional beamforming.

FIG. 13 provides additional context for various embodiments described herein, intended to provide a brief, general description of a suitable operating environment 1300 in which the various embodiments of the embodiment described herein can be implemented. While the embodiments have been described above in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that the embodiments can be also implemented in combination with other program modules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the various methods can be practiced with other computer system configurations, including single-processor or multiprocessor computer systems, minicomputers, mainframe computers, Internet of Things (IoT) devices, distributed computing systems, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

The illustrated embodiments of the embodiments herein can be also practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which can include computer-readable storage media, machine-readable storage media, and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media or machine-readable storage media can be any available storage media that can be accessed by the computer and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media or machine-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable or machine-readable instructions, program modules, structured data or unstructured data.

Computer-readable storage media can include, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD), Blu-ray disc (BD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, solid state drives or other solid state storage devices, or other tangible and/or non-transitory media which can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” herein as applied to storage, memory or computer-readable media, are to be understood to exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.

Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media. The term “modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

FIG. 13 depicts an example operating environment 1300 for implementing various embodiments of the aspects described herein includes a computer 1302, the computer 1302 including a processing unit 1304, a system memory 1306 and a system bus 1308. The system bus 1308 couples system components including, but not limited to, the system memory 1306 to the processing unit 1304. The processing unit 1304 can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures can also be employed as the processing unit 1304.

The system bus 1308 can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 1306 includes ROM 1310 and RAM 1312. A basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer 1302, such as during startup. The RAM 1312 can also include a high-speed RAM such as static RAM for caching data.

The computer 1302 further includes an internal hard disk drive (HDD) 1314 (e.g., EIDE, SATA), one or more external storage devices 1316 (e.g., a magnetic floppy disk drive (FDD) 1316, a memory stick or flash drive reader, a memory card reader, etc.) and a drive 1320, e.g., such as a solid-state drive, an optical disk drive, which can read or write from a disk 1322, such as a CD-ROM disc, a DVD, a BD, etc. Alternatively, where a solid-state drive is involved, disk 1322 would not be included, unless separate. While the internal HDD 1314 is illustrated as located within the computer 1302, the internal HDD 1314 can also be configured for external use in a suitable chassis (not shown). Additionally, while not shown in environment 1300, a solid-state drive (SSD) could be used in addition to, or in place of, an HDD 1314. The HDD 1314, external storage device(s) 1316 and drive 1320 can be connected to the system bus 1308 by an HDD interface 1324, an external storage interface 1326 and a drive interface 1328, respectively. The interface 1324 for external drive implementations can include at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.

The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer 1302, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable storage media above refers to respective types of storage devices, it should be appreciated by those skilled in the art that other types of storage media which are readable by a computer, whether presently existing or developed in the future, could also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.

A number of program modules can be stored in the drives and RAM 1312, including an operating system 1330, one or more application programs 1332, other program modules 1334 and program data 1336. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 1312. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

Computer 1302 can optionally comprise emulation technologies. For example, a hypervisor (not shown) or other intermediary can emulate a hardware environment for operating system 1330, and the emulated hardware can optionally be different from the hardware illustrated in FIG. 13. In such an embodiment, operating system 1330 can comprise one virtual machine (VM) of multiple VMs hosted at computer 1302. Furthermore, operating system 1330 can provide runtime environments, such as the Java runtime environment or the .NET framework, for applications 1332. Runtime environments are consistent execution environments that allow applications 1332 to run on any operating system that includes the runtime environment. Similarly, operating system 1330 can support containers, and applications 1332 can be in the form of containers, which are lightweight, standalone, executable packages of software that include, e.g., code, runtime, system tools, system libraries and settings for an application.

Further, computer 1302 can be enable with a security module, such as a trusted processing module (TPM). For instance, with a TPM, boot components hash next in time boot components, and wait for a match of results to secured values, before loading a next boot component. This process can take place at any layer in the code execution stack of computer 1302, e.g., applied at the application execution level or at the operating system (OS) kernel level, thereby enabling security at any level of code execution.

A user can enter commands and information into the computer 1302 through one or more wired/wireless input devices, e.g., a keyboard 1338, a touch screen 1340, and a pointing device, such as a mouse 1342. Other input devices (not shown) can include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control, or other remote control, a joystick, a virtual reality controller and/or virtual reality headset, a game pad, a stylus pen, an image input device, e.g., camera(s), a gesture sensor input device, a vision movement sensor input device, an emotion or facial detection device, a biometric input device, e.g., fingerprint or iris scanner, or the like. These and other input devices are often connected to the processing unit 1304 through an input device interface 1344 that can be coupled to the system bus 1308, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, a BLUETOOTH® interface, etc.

A monitor 1346 or other type of display device can be also connected to the system bus 1308 via an interface, such as a video adapter 1348. In addition to the monitor 1346, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

The computer 1302 can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) 1350. The remote computer(s) 1350 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer 1302, although, for purposes of brevity, only a memory/storage device 1352 is illustrated. The logical connections depicted include wired/wireless connectivity to a local area network (LAN) 1354 and/or larger networks, e.g., a wide area network (WAN) 1356. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 1302 can be connected to the local network 1354 through a wired and/or wireless communication network interface or adapter 1358. The adapter 1358 can facilitate wired or wireless communication to the LAN 1354, which can also include a wireless access point (AP) disposed thereon for communicating with the adapter 1358 in a wireless mode.

When used in a WAN networking environment, the computer 1302 can include a modem 1360 or can be connected to a communications server on the WAN 1356 via other means for establishing communications over the WAN 1356, such as by way of the Internet. The modem 1360, which can be internal or external and a wired or wireless device, can be connected to the system bus 1308 via the input device interface 1344. In a networked environment, program modules depicted relative to the computer 1302 or portions thereof, can be stored in the remote memory/storage device 1352. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

When used in either a LAN or WAN networking environment, the computer 1302 can access cloud storage systems or other network-based storage systems in addition to, or in place of, external storage devices 1316 as described above, such as but not limited to a network virtual machine providing one or more aspects of storage or processing of information. Generally, a connection between the computer 1302 and a cloud storage system can be established over a LAN 1354 or WAN 1356 e.g., by the adapter 1358 or modem 1360, respectively. Upon connecting the computer 1302 to an associated cloud storage system, the external storage interface 1326 can, with the aid of the adapter 1358 and/or modem 1360, manage storage provided by the cloud storage system as it would other types of external storage. For instance, the external storage interface 1326 can be configured to provide access to cloud storage sources as if those sources were physically connected to the computer 1302.

The computer 1302 can be operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, store shelf, etc.), and telephone. This can include Wireless Fidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.

The above description of illustrated embodiments of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such embodiments and examples, as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described in connection with various embodiments and corresponding Figures, where applicable, it is to be understood that other similar embodiments can be used or modifications and additions can be made to the described embodiments for performing the same, similar, alternative, or substitute function of the disclosed subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

Further to the description above, as it employed in the subject specification, the term “processor” can refer to substantially any computing processing unit or device comprising, but not limited to comprising, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of user equipment. A processor may also be implemented as a combination of computing processing units.

In the subject specification, terms such as “store,” “storage,” “data store,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.

As used in this application, the terms “component,” “system,” “platform,” “layer,” “selector,” “interface,” and the like are intended to refer to a computer-related entity or an entity related to an operational apparatus with one or more specific functionalities, wherein the entity can be either hardware, a combination of hardware and software, software, or software in execution. As an example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration and not limitation, both an application running on a server and the server can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media, device readable storage devices, or machine-readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, which is operated by a software or firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can include a processor therein to execute software or firmware that confers at least in part the functionality of the electronic components.

In addition, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. Moreover, articles “a” and “an” as used in the subject specification and annexed drawings should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.

Additionally, the terms “core-network”, “core”, “core carrier network”, “carrier-side”, or similar terms can refer to components of a telecommunications network that typically provides some or all of aggregation, authentication, call control and switching, charging, service invocation, or gateways. Aggregation can refer to the highest level of aggregation in a service provider network wherein the next level in the hierarchy under the core nodes is the distribution networks and then the edge networks. User equipments do not normally connect directly to the core networks of a large service provider but can be routed to the core by way of a switch or radio area network. Authentication can refer to determinations regarding whether the user requesting a service from the telecom network is authorized to do so within this network or not. Call control and switching can refer determinations related to the future course of a call stream across carrier equipment based on the call signal processing. Charging can be related to the collation and processing of charging data generated by various network nodes. Two common types of charging mechanisms found in present day networks can be prepaid charging and postpaid charging. Service invocation can occur based on some explicit action (e.g., call transfer) or implicitly (e.g., call waiting). It is to be noted that service “execution” may or may not be a core network functionality as third-party network/nodes may take part in actual service execution. A gateway can be present in the core network to access other networks. Gateway functionality can be dependent on the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” “prosumer,” “agent,” and the like are employed interchangeably throughout the subject specification, unless context warrants particular distinction(s) among the terms. It should be appreciated that such terms can refer to human entities or automated components (e.g., supported through artificial intelligence, as through a capacity to make inferences based on complex mathematical formalisms), that can provide simulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploited in substantially any, or any, wired, broadcast, wireless telecommunication, radio technology or network, or combinations thereof. Non-limiting examples of such technologies or networks include Geocast technology; broadcast technologies (e.g., sub-Hz, ELF, VLF, LF, MF, HF, VHF, UHF, SHF, THz broadcasts, etc.); Ethernet; X.25; powerline-type networking (e.g., PowerLine AV Ethernet, etc.); femto-cell technology; Wi-Fi; Worldwide Interoperability for Microwave Access (WiMAX); Enhanced General Packet Radio Service (Enhanced GPRS); Third Generation Partnership Project (3GPP or 3G) Long Term Evolution (LTE); 3GPP Universal Mobile Telecommunications System (UMTS) or 3GPP UMTS; Third Generation Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB); High Speed Packet Access (HSPA); High Speed Downlink Packet Access (HSDPA); High Speed Uplink Packet Access (HSUPA); GSM Enhanced Data Rates for GSM Evolution (EDGE) Radio Access Network (RAN) or GERAN; UMTS Terrestrial Radio Access Network (UTRAN); or LTE Advanced.

What has been described above includes examples of systems and methods illustrative of the disclosed subject matter. It is, of course, not possible to describe every combination of components or methods herein. One of ordinary skill in the art may recognize that many further combinations and permutations of the disclosure are possible. Furthermore, to the extent that the terms “includes,” “has,” “possesses,” and the like are used in the detailed description, claims, appendices and drawings such terms are intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.

While the various embodiments are susceptible to various modifications and alternative constructions, certain illustrated implementations thereof are shown in the drawings and have been described above in detail. It should be understood, however, that there is no intention to limit the various embodiments to the specific forms disclosed, but on the contrary, the intention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope of the various embodiments.

In addition to the various implementations described herein, it is to be understood that other similar implementations can be used, or modifications and additions can be made to the described implementation(s) for performing the same or equivalent function of the corresponding implementation(s) without deviating therefrom. Still further, multiple processing chips or multiple devices can share the performance of one or more functions described herein, and similarly, storage can be affected across a plurality of devices. Accordingly, the embodiments are not to be limited to any single implementation, but rather are to be construed in breadth, spirit and scope in accordance with the appended claims. 

What is claimed is:
 1. A method, comprising: confirming, by site launching equipment comprising a processor, installation of components of a base station, resulting in a confirmed installation; based on the confirmed installation, facilitating, by the site launching equipment, integrating the base station into a communications network; in response to the integrating, launching, by the site launching equipment, operation of the base station for a testing of performance of the base station, the testing resulting in a tested base station; and activating, by the site launching equipment, the tested base station for use by authorized user equipment via the communications network.
 2. The method of claim 1, wherein facilitating the integrating of the base station is based on a process comprising: detecting a condition associated with the integrating that has a likelihood of causing a defined adverse event that has least a threshold likelihood; and instructing the base station to perform a self-correcting network process at the base station to reduce the likelihood to being less than the threshold likelihood.
 3. The method of claim 1, wherein the testing of the performance comprises: selecting a geographic boundary around the base station; and receiving, from user equipment within the geographic boundary, a test result based on communications with the base station by the user equipment.
 4. The method of claim 1, further comprising, obtaining, by the site launching equipment, notice data representative of a notice of completion of a regulatory milestone for the installation of the components of the base station, wherein confirming the installation process is triggered in response to obtaining the notice data.
 5. The method of claim 4, wherein the notice of completion comprises a notice that the base station complies with a public safety geolocation requirement.
 6. The method of claim 1, wherein integrating the base station into the communications network comprises determining that launching the operation of the base station has at least a threshold likelihood of causing a defined adverse result.
 7. The method of claim 1, wherein activating the tested base station comprises determining that the activating has at least a threshold likelihood of causing a defined adverse result.
 8. The method of claim 7, wherein the determining that the activating has at least the threshold likelihood is based on profile data representative of a submarket profile of the tested base station.
 9. The method of claim 8, wherein the submarket profile defines a minimum quality of service of the tested base station.
 10. The method of claim 1, further comprising: after activating the tested base station and based on a detected condition, suspending, by the site launching equipment, the operation of the base station; based on the detected condition, facilitating, by the site launching equipment, adjusting a parameter of the operation of the base station; and based on the detected condition being determined to have been eliminated by adjusting the parameter, determining, by the site launching equipment, that the activating does not have at least a threshold likelihood of causing a defined adverse result.
 11. The method of claim 1, wherein confirming the installation of the components of the base station comprises comparing an indication of a present value of an operation parameter to a specified value of a specified parameter determined from an installation specification, and, based on a result of the comparing, confirming the present value equals the specified value.
 12. Network equipment, comprising: a processor; and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising: transmitting, to network implementation equipment, information usable to confirm installation of components of the network equipment; in response to the transmitting, receiving, from the network implementation equipment, confirmation data representing that the installation of the component has been confirmed by the network implementation equipment, receiving, from the network implementation equipment, first instruction data representing a first instruction to integrate the network equipment into a telecommunications network, receiving, from the network implementation equipment, second instruction data representing a second instruction to launch an operation of a transceiver used by the network equipment to test a performance of communicating with the network implementation equipment using the transceiver, and based on test data generated by the network equipment representing a first assessment of the performance by the network equipment, and based on assessment data received from the network implementation equipment and representing a second assessment of the performance, deploying the network equipment for general use by mobile devices via the telecommunications network.
 13. The network equipment of claim 12, wherein the assessment data comprises likelihood data representing a likelihood that the deploying will cause an adverse event with respect to a threshold likelihood that the adverse event will occur.
 14. The network equipment of claim 13, wherein the threshold likelihood is based on profile data representing a market profile associated with the network equipment.
 15. The network equipment of claim 14, wherein the profile data comprises quality of service data representing a minimum quality of service to be enabled by the network equipment.
 16. The network equipment of claim 12, wherein transmitting the information usable to confirm the installation of the components is in response to request data representing an inquiry received from the network implementation equipment, and wherein the request data was generated by the network implementation equipment based on a determination that a regulatory milestone for the installation of the components of the network equipment has been reached.
 17. The network equipment of claim 12, wherein generation of the test data by the network equipment comprises: receiving, from a mobile device, result data representing a test result based on the mobile device communicating with the network equipment within a geographic boundary associated with the network equipment; and generating the test data based on the result data.
 18. A non-transitory machine-readable medium, comprising executable instructions that, when executed by a processor of a system, facilitate performance of operations, comprising: based on an indication that base station equipment complies with a regulatory requirement for use in a mobile network, confirming that components of the base station equipment have been installed, wherein the confirming comprises comparing a specified installation parameter to a measured parameter determined for the base station equipment, and wherein the confirming results in a confirmed installation of the base station equipment; based on the confirmed installation, facilitating commencing operation of the base station equipment to test a performance of the base station equipment, wherein a result of testing the performance is used to estimate a likelihood of an activation of the base station equipment for usage by user devices in the mobile network causing a defined adverse event; and based on the likelihood being less than a defined threshold, facilitating activating the base station equipment for the usage in mobile network.
 19. The non-transitory machine-readable medium of claim 18, wherein the indication is obtained from a record stored in a data store comprising milestone data representative of installation milestones, wherein the record indicates compliance with the regulatory requirement.
 20. The non-transitory machine-readable medium of claim 18, wherein the defined adverse event comprises operation of the base station equipment without at least a quality of service specified by profile data representative of a submarket profile of the base station equipment. 